Airport taxiway navigation system

ABSTRACT

A method and system for providing taxiway navigational information to a crewmember of an airplane taxiing at an airport. An airport taxiway navigation system (“ATNS”) that executes on an onboard computer system that displays a map of the taxiways of an airport, receives the name of each taxiway of the taxi route specified by the taxi clearance, and highlights the taxiways on a displayed map to provide a visual indication of the cleared taxi route for the crewmembers.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application No. 60/358,327 and U.S. Provisional Application No. 60/358,339 both filed Feb. 19, 2002, which are incorporated herein by reference in their entirety. This application is a divisional of U.S. patent application Ser. No. 10/369,187 filed Feb. 19, 2003 now U.S. Pat. No. 7,813,845 which is incorporated herein by reference in its entirety.

BACKGROUND

The described technology relates generally to navigation systems and particularly to a navigation system for an airplane taxiing at an airport.

When an airplane lands at an airport, the ground control personnel for that airport provide a taxi clearance to the crewmembers of the airplane. The taxi clearance specifies a taxi route that the airplane is to use in taxiing from the runway, to the destination gate. Ground control personnel select a taxi clearance that facilitates taxiing from the landing runway to the destination gate or from the departing gate to the takeoff runway, that reduces congestion on the taxiways, and enhances safety. The ground control personnel radio the taxi route to the crewmembers, providing the names of the taxiways of the cleared taxi route. The names of the taxiways typically consist of one or two letters followed by an optional number. Example names of taxiways at an airport may be “A1,” “A2,” “E1,” “E2,” and “WC.” The ground control personnel may identify a taxi route by saying “echo two alpha one charlie three.” A crewmember may write down the names of the taxiways and then use those taxiways to taxi the airplane to the gate. Each taxiway is identified by one or more signs marked with its respective name. While taxiing, a crewmember can compare the names on the signs with the written-down names.

It is, of course, important for an airplane to follow its cleared taxi route. The typical taxiing process is, however, subject to human error. For example, a crewmember may incorrectly hear the name of a taxiway or may incorrectly write down the name of a taxiway. In addition, since adverse weather conditions may affect the visibility of the names of the taxiways on the signs, a crewmember may incorrectly identify a taxiway. As a result of these errors, a crewmember may inadvertently taxi the airplane onto an incorrect taxiway.

In addition to taxiing on the correct taxiways, it is important for crewmembers to recognize and stop their airplane at holdshort lines. A holdshort line is typically found at the intersection of a taxiway and a runway or at the intersection of a low-speed taxiway and a high-speed taxiway. A taxiing airplane should stop at each holdshort line until clearance is received from ground control to allow faster moving airplanes to pass.

It would be desirable to have a taxiing navigation system that would help ensure that the crewmembers of a taxiing airplane correctly receive the cleared taxi route, correctly follow that taxi route, and stop at holdshort lines as appropriate.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a user interface of an onboard computer system executing the software of the airport taxiway navigation system (“ATNS”).

FIG. 2 illustrates the user interface of the ATNS after a crewmember has identified the first taxiway of a cleared taxi route.

FIG. 3 illustrates the user interface of the ATNS after the crewmember has identified the second taxiway of the cleared taxi route.

FIG. 4 illustrates the user interface of the ATNS after the crewmember has identified the third taxiway of the cleared taxi route.

FIGS. 5-8 illustrate user interfaces of the ATNS system as the crewmember identifies the remaining taxiways of the cleared taxi route.

FIG. 9 illustrates the user interface of the ATNS in gate input mode.

FIG. 10 illustrates the user interface of the ATNS after the crewmember has selected destination concourse.

FIG. 11 illustrates the user interface of the ATNS after the crewmember has paged to desired destination gate.

FIG. 12 illustrates the user interface of the ATNS after the crewmember has selected the destination gate.

FIGS. 13-15 illustrate the user interface of the ATNS showing the position and heading of the airplane as it taxis.

FIG. 15A illustrates the user interface of the ATNS when an airport map is displayed in the align-to-runway mode.

FIG. 15B illustrates the user interface of the ATNS with annotations displayed.

FIG. 16 is a block diagram illustrating components of the ATNS in one embodiment.

FIG. 17 is a flow diagram illustrating the processing of an initialize ATNS component.

FIG. 18 is a flow diagram illustrating the processing of the taxi route selection component of the ATNS.

FIG. 19 is a flow diagram illustrating the processing of the gate selection component of the ATNS.

FIG. 20 is a flow diagram illustrating the processing of the preferred route selection component of the ATNS.

FIG. 21 is a flow diagram of the airplane tracking component of the ATNS.

FIG. 22 is a flow diagram illustrating the processing of the estimate position and heading component of the ATNS.

FIG. 23 is a flow diagram illustrating the processing of the evaluate horizontal limit component of the ATNS.

DETAILED DESCRIPTION

A method and system for providing taxiway navigational information to a crewmember of an airplane taxiing at an airport is provided. In one embodiment, an airport taxiway navigation system (“ATNS”) that executes on an onboard computer system displays a map of the taxiways of an airport (e.g., an airport diagram), receives the name of each taxiway of the taxi route specified by a taxi clearance, and highlights the taxiways on the displayed map to provide a visual representation of the cleared taxi route for the crewmembers (or, more generally, users). The ATNS may also receive position and heading information, for example, from the Avionics or Aircraft System Bus (“AASB”), and may superimpose an indication of the current position and heading of the airplane on the displayed map. In this way, crewmembers can track the taxiing of the airplane so they will know when the airplane is approaching the next taxiway in the cleared taxi route, know which way to turn, and know whether the airplane has deviated from the cleared taxi route.

The ATNS may receive the cleared taxi route either by manual input from a crewmember or by input from a ground control computer system. A crewmember may input the taxiways of the cleared taxi route in various ways. For example, the ATNS may display the names of all taxiways at the airport and allow a crewmember to manually select the taxiways of the cleared taxi route. In one embodiment, the ATNS may, after each taxiway is selected, display only the names of the next logically possible taxiways. For example, the next logically possible taxiways might be those taxiways that intersect the last selected taxiway. The ATNS may order the displayed taxiway names alphabetically or based on the likelihood of their being the next selected taxiway. For example, if the ATNS knows the destination gate, it may order the taxiway names based on the distance from the runway through each taxiway to the destination gate. The ATNS may allow a crewmember to select a taxiway by pressing a button (e.g., a hardware button or a soft button displayed on a touch-panel display) or by pointing to the taxiway when the map is displayed on a touch-panel display. As the crewmember selects the taxiways, the ATNS may highlight them on the display. The ATNS may also allow a crewmember to enter the taxi route into a taxi route text box using a keypad. For example, the crewmember may enter “E2, A1, C3” as the taxi route is provided by ground control. In one embodiment, the ATNS provides a “virtual keypad” for entry of the taxi route. A virtual keypad is a pad of numbers and letters displayed on a display (e.g., a touch-panel display) to support data entry. When the crewmember indicates that a taxi route is to be input, the ATNS displays the virtual keypad. Once the taxi route is accepted, the ATNS removes the keypad and displays an airport diagram with the filled-in taxi route text box. As the taxiways of the cleared taxi route are input (e.g., manually), the ATNS highlights the taxiways on the displayed map and may display the name of the taxiway in the taxi route text box. The taxi route text box displays the names of the taxiways in the cleared taxi route and may be used by the crewmember when confirming the cleared taxi route with ground control. In addition, the ATNS may highlight the name of a taxiway in the taxi route text box as the airplane taxis on that taxiway, and the ATNS may provide an additional highlight (e.g., blinking) of that taxiway on the map. In this way, crewmembers will have enhanced situational awareness during taxiing at an airport.

In one embodiment, the ATNS may receive the identity of a gate and runway at the beginning and end of a taxi route input by a crewmember. To facilitate entry of gate information by a crewmember, the ATNS may display the names of the concourses of the airport and allow a crewmember to select a concourse. After the concourse is selected, the ATNS displays the names of the gates for the selected concourse and allows the crewmember to select the destination or departing gate. The ATNS then highlights the gate on the displayed map. The ATNS displays the name of the runways so that a crewmember can select the landing or takeoff runway.

A ground control computer may electronically (e.g., using radio frequency) transmit taxi clearance information to the flight management computer of the airplane in one embodiment. If so, the ATNS may retrieve the cleared taxi route, gate, and runway directly from the flight management computer. In this way, human error from incorrectly hearing or entering a cleared taxi route, gate, and runway is avoided.

In an alternate embodiment, the ATNS allows the map to be displayed in static mode or dynamic mode. In static mode, the map is held stationary and an indication (e.g., graphic representation of an airplane) of the current position of the airplane as it taxis moves relative to the displayed map. One example of the static mode is referred to as “north up mode,” where the top of the display represents north. In dynamic mode, the display of the map moves as the airplane taxis, and the current position of the airplane is shown as a fixed position on the display. One example of the dynamic mode is referred to as a “heading up mode.” The ATNS may allow a crewmember to toggle between a dynamic and static mode.

In one embodiment, the ATNS allows the map to be displayed in an “align-to-runway” mode, which is another example of a static mode display of the map. When in the align-to-runway mode, the ATNS displays the map with a selected runway aligned vertically and centered horizontally. A crewmember can selected the align-to-runway mode as an alternative to the heading up and north up modes. The ATNS may automatically select the align-to-runway mode when an airplane is approaching a runway for landing. When on approach, the airplane's heading may not be aligned with the runway, for example, because of crosswinds (i.e., referred to as “crabbing”). The heading alignment may be several degrees offset from the runway alignment. If the ATNS was displaying the map in heading up mode, the landing runway might not even be visible on the display because of the offset. Also, when an airplane lands, it might change its heading rapidly to align with the runway. This rapid change in alignment may result in a sudden and distracting change in the orientation of the map. By using the align-to-runway mode, the ATNS ensures that the runway is visible on the map during the approach and that a sudden change in map orientation does not occur when the airplane lands.

In one embodiment, the ATNS may automatically transition from align-to-runway mode to heading up mode when the airplane lands. This transition is smooth because, when the heading is aligned with the runway, both modes display the same orientation of the map. The ATNS may also use the align-to-runway mode when an airplane takes off. If the heading up mode is used when an airplane takes off, then a sudden change in map orientation will occur if the airplane has a rapid heading change. To avoid this sudden change in map orientation, the ATNS may automatically switch from heading up mode to align-to-runway mode as the airplane takes off.

The align-to-runway mode can also be used by a crewmember to plan the landing of the airplane at an airport. The runway to align to (e.g., the landing runway) can be selected manually by a crewmember (e.g., by pointing to the runway) or automatically based on information retrieved from the AASB. In the align-to-runway mode, the crewmember can communicate with the ground control personnel while viewing the airport from the perspective of the landing runway. This align-to-runway view may make it easier for a crewmember to point to the taxiways when defining the cleared taxi route to the ATNS.

In another embodiment, the ATNS allows for the defining of preferred taxi routes for an airport. Each preferred taxi route may have a name associated with it or may be identified by the sequence of its taxiway names. If a cleared taxi route corresponds to a preferred taxi route, a crewmember need only select the preferred taxi route and need not individually identify each taxiway of the cleared taxi route. In addition, the ATNS may allow a crewmember or an operations and aircraft maintenance person to define new preferred taxi routes in much the same way as a cleared taxi route is specified. The virtual keypad can be used to enter a name for a preferred taxi route. The use of preferred taxi routes helps reduce the time it takes a crewmember to specify the cleared taxi route to the ATNS.

In one embodiment, the ATNS system may notify crewmembers when position information indicates that their airplane is deviating from the cleared taxi route or is nearing the edge of a taxiway. The ATNS retrieves the position information (e.g., from the AASB) and identifies the current taxiway. If the current taxiway is not on the cleared taxi route, then the ATNS may provide a visual or audio notification to the crew. The ATNS may also compare the current position of the airplane to the edge of the current taxiway. If the current position indicates that the airplane is within a certain distance of the edge of the taxiway (e.g., a horizontal integrity limit), then the ATNS may provide a visual or audio notification to the crew.

In another embodiment, the ATNS can identify the airport at which the airplane is landing or taking off based on position information retrieved from the AASB. The ATNS provides a mapping of position information to supported airports. Once the airport is identified from the mapping, the ATNS retrieves and displays a map for that airport. The ATNS also uses the identification of the airport to retrieve taxiway, preferred taxi routes, runway, and gate information. In an alternate embodiment, the ATNS may retrieve the identity of the airport from the AASB.

A crewmember may start the ATNS application through a main menu that lists the applications available on the onboard computer system. Alternatively, the ATNS application can be automatically started based on various aircraft events. For example, the ATNS application may be started when the airspeed of the aircraft is less than 100 knots or if Weight On Wheels (“WOW”) is detected, as indicated by the AASB. It may also be started when a certain signal is received from a ground control computer system.

In one embodiment, the ATNS may estimate (e.g., extrapolate) the current position and heading of an airplane as it taxis based on previous position and heading information received from the AASB. For example, the ATNS may receive position and heading information from the AASB once every second. If the ATNS updates the representation of the position, speed, and heading of the airplane only once a second, then when the airplane is taxiing at high speed or the map of the airport is shown zoomed-in, the positions of the airplane may tend to look discontinuous (e.g., jittery). To avoid this visual discontinuity, the ATNS may update the indicated position and heading more frequently (e.g., 10 times a second) based on estimates of the current position and heading.

The ATNS in one embodiment allows a crewmember to add various types of annotations to the map. For example, a crewmember when planning the taxiing at an airport may use a freehand drawing tool to cross out those taxiways that are closed (e.g., because of repairs or ice). The annotations may be made using freehand drawings, icon placement, text boxes, and so on. The ATNS associates each annotation with a position on the map so that the annotations can be appropriately displayed as the map is scaled and panned or is displayed in static or dynamic modes. In freehand mode, the crewmember can use a pointing device to draw on the map. Some pointing devices allow for continuous selection of points, while other pointing devices allow for only discrete selection of a point. A touch-panel display or a light-pen display allows for the continuous selection of points as the crewmember moves the pointing device, for example, to mark a line. Certain pointing devices, in contrast, only allow a discrete point to be selected at a time. With such a pointing device, the ATNS allows a crewmember to select two points and then indicate to draw a line between the points. When more than two points are selected, the points are vertices of lines connecting the points. In icon placement mode, the ATNS allows a crewmember to place icons on the map as annotations. For example, a crewmember may drag and drop an icon of the international “not” symbol over a taxiway that is closed. The ATNS then displays that icon over the taxiway whenever the taxiway is displayed. In text box mode, the crewmember can select a position on the map and enter text in a text box that is associated with that position. The crewmember can enter the text using a virtual keypad. The ATNS displays the text box whenever that associated position on the map is displayed. The ATNS may allow a crewmember to toggle between displaying (i.e., unhiding) and not displaying (i.e., hiding) the annotations. The ATNS may also allow a crewmember to manually indicate when some or all of the annotations for a map of an airport are to be discarded. Alternatively, the ATNS may automatically discard all the annotations for the take off or landing airports as part of the flight initialization process. In one embodiment, some annotations may be designated as “persistent” to indicate that they are not to be automatically discarded between flights.

FIGS. 1-15 illustrate the user interface of the ATNS in one embodiment. FIG. 1 illustrates the user interface of an onboard computer system executing the software of the airport taxiway navigation system (“ATNS”). Image 100 includes map display area 101, a taxi route text box 102, taxiway/gate buttons 111-120, menu buttons 121-126, map control buttons 130-135, and control buttons 140-145. The map display area 101 displays the map of an airport. The taxiway/gate buttons are used to select the various taxiways of a taxi route, or the concourse and gate, depending on the current mode of the ATNS. The ATNS may be in one of several modes, such as a taxi route input mode, a gate input mode, a runway input mode, or an airplane tracking mode. As illustrated, the ATNS has displayed the names of taxiways to the right of taxiway/gate buttons 111-115. In this example, a crewmember selects taxiway/gate button 112 corresponding to the taxiway “W6” as the first taxiway of the taxi route. The menu buttons 121-126 are used to select the different modes of the ATNS, as indicated by the text corresponding to the buttons. For example, menu button 123 when selected places the ATNS in a gate input mode. The map control buttons 130-135 are used to zoom in and out of the map and scroll the map up and down or left and right. The control buttons 140-145 may be used to control the display associated with the taxiway/gate buttons 111-120. For example, when the number of taxiways that are available to be selected exceeds 10 (i.e., the number of taxiway/gate buttons), then a crewmember selects the page up button 143 or the page down button 144 to display a next or previous group of taxiways. The actual function of the control buttons may depend on the current mode of the ATNS.

In one embodiment, the ATNS uses maps of an airport generated from actual satellite images of the airport to help ensure the accuracy of the map. To generate the map, various landmarks of the airport may be identified on the satellite image. The actual measurements of the airport objects (e.g., runway, taxiway, and concourses) are then derived from the landmarks. Such maps may be represented as vectors that define the boundaries of airport objects. The ATNS may also have a mapping between the airport objects and their names (e.g., “E1” maps to the vectors defining that taxiway). The ATNS may use this mapping to highlight or label the airport objects on the map. In one embodiment, the labels of the airport objects are displayed horizontally on the display, regardless of the orientation of the map, to facilitate readability.

FIG. 2 illustrates the user interface of the ATNS after a crewmember has identified the first taxiway of a cleared taxi route. As shown in FIG. 1, the crewmember selected taxiway “W6” as the first taxiway of the cleared taxi route. The ATNS has highlighted taxiway “W6” by, for example, superimposing a black line 201 on the image of the taxiway. In addition, the ATNS has displayed the name of the taxiway in the taxi route text box 102. The ATNS has also displayed the names of the logically possible next taxiways in the taxi route. In this example, the logically possible next taxiways are taxiway “WP” and taxiway “V6,” as displayed to the right of taxiway/gate buttons 111 and 112. In this example, the crewmember selects taxiway “WP.”

FIG. 3 illustrates the user interface of the ATNS after a crewmember has identified the second taxiway of the cleared taxi route. The ATNS has now highlighted taxiway “W6” by, for example, superimposing a black line 301. In this example, the entire taxiway is highlighted because the ATNS does not yet know whether the cleared taxi route will be to the left or right of taxiway “W6.” The ATNS has added the name of taxiway “W6” to the taxi route text box 102. The ATNS has also displayed the names of the logically possible next taxiways. For example, the ATNS has displayed the name of taxiway “V4” to the left of taxiway/gate button 116. In this example, the crewmember selects taxiway “NC1” as the next taxiway.

FIG. 4 illustrates the user interface of the ATNS after the crewmember has identified the third taxiway of the cleared taxi route. The ATNS has now highlighted taxiway “NC1” by, for example, superimposing a black line 401. The ATNS has also removed the highlighting for that portion of taxiway “WP” that is not on the cleared taxi route. The ATNS has added the name of taxiway “NC1” to the taxi route text box 102. The ATNS has displayed the names of the next logically possible taxiways adjacent to taxiway/gate buttons 111-113. In this example, the crewmember selects taxiway “A7” as the next taxiway.

FIGS. 5-8 illustrate user interfaces of the ATNS system as the crewmember identifies the remaining taxiways of the cleared taxi route. The ATNS provides these user interfaces in a manner similar to that illustrated by FIGS. 1-4. The highlighted (e.g., black) line 801 in FIG. 8 represents the complete cleared taxi route. The cleared taxi route comprises taxiways “W6,” “WP,” “NC1,” “A7,” “E1” “EP,” and “CX,” as indicated by the taxi route text box 102. In this example, the crewmember selects menu button 125 to switch from the taxiway input mode to the gate input mode of the ATNS.

FIG. 9 illustrates the user interface of the ATNS in gate input mode. The ATNS displays the names of the concourses adjacent to taxiway/gate buttons 111-115. For example, taxiway/gate button 111 corresponds to concourse “C.” The function of menu button 123 has changed to enter taxi route input mode. This button allows the ATNS to toggle between taxi route input mode and gate input mode. In this example, the crewmember selects taxiway/gate button 114 corresponding to concourse “F.”

FIG. 10 illustrates the user interface of the ATNS after the crewmember has selected the destination concourse “F”. The ATNS displays the names of the gates of the selected concourse adjacent to taxiway/gate buttons 111-120. In this example, concourse “F” has more than 10 gates. Thus, the crewmember uses the page up button 143 and the page down button 144 to page through the list of gates. Although not highlighted in this example, the ATNS may also highlight the selected concourse on the map.

FIG. 11 illustrates the user interface of the ATNS after the crewmember has paged to the desired gate. In this example, the crewmember selects gate “F42”.

FIG. 12 illustrates the user interface of the ATNS after the crewmember has selected the destination gate. The ATNS indicates the destination gate by highlight 1201. The crewmember may then select the display on moving map button 126 to switch to a dynamic mode. The ATNS may automatically enter an airplane tracking mode. One skilled in the art will appreciate that the ATNS may be in airplane tracking mode concurrently with other modes to show the current position and heading of the airplane even before or during entry of the cleared taxi route.

FIGS. 13-15 illustrate the user interface of the ATNS showing the position and heading of the airplane as it taxis. In FIG. 13 a triangle 1301 indicates the position and heading of the airplane. In an alternate embodiment, an image of an airplane may be displayed instead of a triangle. As discussed above, the displayed position and heading of the airplane may be estimated to help smooth the transition from one position and heading reading to the next position and heading reading. Although not illustrated, the ATNS may highlight the names of the taxiways in the taxi route text box 102 as the airplane enters each taxiway to show progress through the cleared taxi route. As the airplane taxis, the ATNS may provide visual and audio notifications of alert conditions, such as nearing the edge of a taxiway, entering a wrong taxiway, or approaching a holdshort line.

FIG. 15A illustrates the user interface of the ATNS when an airport map is displayed in the align-to-runway mode. In this example, the airplane is on approach to runway 16L. The ATNS displays runway 16L 1550 vertically and centered horizontally on the display. The compass 1551 indicates that the airplane is approaching from the north. When the airplane lands, for example, as detected by WOW, the ATNS may automatically switch to heading up mode.

FIG. 15B illustrates the user interface of the ATNS with annotations displayed. In this example, a crewmember has selected the freehand drawing mode and annotated portions of the cleared taxi route. The line 1561 indicates the cleared taxi route. The “Xs” 1562 indicate taxiways or portions of taxiways not on the cleared taxi route. The exclamation point with the circle 1563 indicates an area of concern noted by a crewmember. For example, the area of concern may indicate that a construction project is in progress near that position. The circle 1564 indicates the destination gate. The “undo” button 1565 allows a crewmember to remove the freehand drawing segment (e.g., a circle) or other annotation that was last placed on the map. The “clear all” button 1566 allows a crewmember to remove all the annotations from the map.

FIG. 16 is a block diagram illustrating components of the ATNS in one embodiment. The ATNS may include software components such as a main ATNS component 1601, a taxi route selection component 1602, a gate selection component 1603, an airplane tracking component 1604, a define preferred route component 1605, a flight management control interface 1606, and a map attributes component 1607. In addition, the ATNS may include various data stores such as an airport location data store 1610, an airport map data store 1611, an airport taxiway data store 1612, an airport gate data store 1613, a preferred route data store 1614, and an airport satellite map data store 1615. The data stores may be implemented using files and databases and may contain various data structures. The main ATNS component provides for initialization of the ATNS and selection of the various modes of the ATNS. The taxi route selection component controls the input of the cleared taxi route by a crewmember. The gate selection component controls the input of the destination gate by a crewmember. The airplane tracking component periodically retrieves position and heading information from the AASB and displays an indication of the current position and heading of the airplane. The airplane tracking component may provide various alerts, such as when the airplane is getting near the edge of a taxiway or near another airplane (assuming it has access to the position information of other airplanes). The define preferred route component allows a crewmember to define new preferred taxi routes. The flight management control interface provides access to flight management information, such as position and heading. The flight management control interface may also provide access to taxiing information (e.g., cleared taxi route) provided by the ground control computer system to the flight management control system of the airplane. The map attribute component is used to control various attributes of the map, such as selection of static or dynamic modes, selection of a satellite view mode, and zooming and scrolling of the map. In satellite view mode, the ATNS displays a satellite image of the airport to help orient the crewmembers. The airport location data store contains a list of supported airports along with location information for each airport. The ATNS may use this information to identify the landing or takeoff airport. The airport map data store contains a map of each supported airport. Each map may be stored as vectors describing the boundaries of the runways, taxiways, concourses, and so on, of each airport. The airport taxiway data store identifies the name of each taxiway and other ways of the corresponding airport and may include additional information, such as the logically possible next taxiways for each taxiway. The airport taxiway store contains a mapping of taxiway names to corresponding information in the airport map data store. The airport taxiway data store may also include information describing holdshort lines and identifying major and minor taxiways. In one embodiment, the ATNS allows a crewmember to input only the major taxiways of the cleared taxi route and automatically identifies the corresponding minor taxiways. The airport gate data store identifies the name of the concourses and gates of the airport along with a mapping to the corresponding information in the airport map data store. The preferred route data store contains the currently define preferred routes for each airport. The airport satellite map data store contains a satellite image of the supported airports.

The ATNS software may execute on an onboard ATNS computer that includes a central processing unit, memory, input devices (e.g., pointing device, touch-panel display, and physical buttons), output devices (e.g., display devices and speakers), and storage devices (e.g., flash EPROM and disk drives). The memory and storage devices are computer-readable media that may contain instructions and data structures that implement the ATNS. The ATNS computer may be connected to other onboard devices (e.g., the flight management computer) via a bus or point-to-point connection to retrieve information (e.g., position and heading) from and provide information (e.g., destination gate) to other devices (e.g., printer). Since the ATNS is typically only used when taxiing before takeoff or after landing, the ATNS may be one of several applications that are available on the ATNS computer for use during flight or while not taxiing. Alternatively, the ATNS computer may not even be an installed onboard computer connected to other devices but may, for example, be a stand-alone laptop computer located in the cockpit. In such a case, the laptop computer may have a global positioning device. One skilled in the art will appreciate that the function of the ATNS may be provided by a computer that is remote from the airplane. For example, a ground control computer executing the ATNS may generate and send data about the airport, cleared taxi route, and airplane position to be displayed on an onboard monitor. The display images provided by such a ground control computer may also show positions of other airplanes.

FIGS. 17-23 are flow diagrams that illustrate the processing of the components of the ATNS in one embodiment. The flow diagrams illustrate the overall function of the ATNS. One skilled in the art will appreciate, however, that the functions may be implemented in many different ways, and the components and data stores can be organized in many different ways. FIG. 17 is a flow diagram that illustrates the processing of an initialize ATNS component. This component may be a subcomponent of the main ATNS component. This component identifies the airport (i.e., landing or takeoff) and displays the initial user interface for input of the cleared taxi route. In block 1701, the component receives position, speed, and heading information from the AASB. In block 1702, the component identifies the airport based on comparison of the position information and the location information in the airport location data store. Alternatively, the component may retrieve the identity of the airport from the AASB or receive it from a crewmember. In block 1703, the component retrieves the airport map for the airport from the airport map data store. In block 1704, the component retrieves the taxiway information for the airport from the airport taxiway data store. In block 1705, the component retrieves the preferred taxi routes from the preferred route data store for the selected airport. In block 1706, the component receives an identification of the runway. In one embodiment, a crewmember may input the runway identification. Alternatively, it may be retrieved from the AASB. In block 1707, the component displays the airport map. In block 1708, the component displays the names of the logically possible next taxiways adjacent to the taxiway/gate buttons and then completes.

FIG. 18 is a flow diagram that illustrates the processing of the taxi route selection component of the ATNS when an airplane lands. The taxi route selection component controls the entry of the taxiways of the cleared taxi route by a crewmember. In block 1801, the component identifies the logically possible next taxiways for the landing runway based on the information in the airport taxiway data store. The component may alternatively give the crewmember an option to select any one of the taxiways at the airport. In blocks 1802-1809, the component loops, allowing the crewmember to input the next taxiway of the cleared taxi route. In block 1802, the component displays the names of the logically possible next taxiways adjacent to the taxiway/gate buttons. Although not shown by this flow diagram, the component may allow the crewmember to page through the list of taxiways. In block 1803, the component receives the selection of the next taxiway from a crewmember. In block 1804, the component adds the selected taxiway to the taxi route. In block 1805, the component retrieves a mapping for the selected taxiway to the displayed map. In block 1806, the component uses the retrieved mapping to highlight the next taxiway of the taxi route. In block 1807, the component adds the name of the selected taxiway to the taxi route text box. In decision block 1808, if all the taxiways of the taxi route have already been selected, then the component completes, else the component continues at block 1809. In block 1809, the component identifies the logically possible next taxiways for the last selected taxiway and then loops to block 1802 to allow a crewmember to select the next taxiway.

FIG. 19 is a flow diagram that illustrates the processing of the gate selection component of the ATNS when landing. The gate selection component allows a crewmember to designate the destination gate. In block 1901, the component retrieves the gate information for the airport from the airport gate data store. In block 1902, the component displays the concourse names adjacent to the taxiway/gate buttons. In block 1903, the component receives the selection of a concourse from a crewmember. In block 1904, the component highlights the selected concourse on the map. In block 1905, the component displays the names of the gates for the selected concourse adjacent to the taxiway/gate buttons. In block 1906, the component receives the selection of the destination gate from a crewmember. In block 1907, the component highlights the selected gate on the map and then completes.

FIG. 20 is a flow diagram that illustrates the processing of the preferred route selection component of the ATNS. This component allows a crewmember to select a preferred taxi route as the cleared taxi route. In block 2001, the component retrieves the preferred taxi routes for the landing runway of the landing airport (or for the departing gate when taking off). In block 2002, the component displays a list of the preferred, taxi routes. In block 2003, the component receives the selection of a preferred taxi route from a crewmember. In blocks 2004-2007, the component loops, highlighting each taxiway of the preferred taxi route. In block 2004, the component selects the next taxiway of the preferred taxi route. In decision block 2005, if all the taxiways of the preferred taxi route have already been selected, then the component completes, else the component continues at block 2006. In block 2006, the component retrieves a mapping for the selected taxiway to the airport map. In block 2007, the component highlights the selected taxiway and loops to block 2004 to select the next taxiway of the selected preferred taxi route.

FIG. 21 is a flow diagram of the airplane tracking component of the ATNS. This component may be automatically executed periodically (e.g., every one-tenth of a second) to indicate the new position of the airplane. Since the position and heading information of the AASB may be updated less frequently, this component estimates the position and heading information in between AASB readings. In block 2101, the component retrieves the position and heading information from the AASB. In block 2102, the component invokes a component to estimate the current position and heading. In block 2103, the component invokes a component to evaluate the horizontal limit of the current taxiway. In block 2104, the component displays an indication of the airplane at the estimated position and heading. In decision block 2105, if the airplane is not within the horizontal limit, then the component outputs an alert in block 2106 before completing.

FIG. 22 is a flow diagram that illustrates the processing of the estimate position and heading component of the ATNS. This component may be passed the last retrieved heading and position information and estimates the current position and heading of the airplane. In decision block 2201, if the retrieved position and heading information is different from the last retrieved position and heading information, then new information is available and the component continues at block 2202, else the component continues at block 2204. In block 2202, the component saves the retrieved position and heading information. In block 2203, the component initializes a timer to indicate the time since the last new position and heading information was retrieved. This timer is used to estimate the position and heading. The component then returns the new position and heading information as the estimated heading and position information. In block 2204, the component increments the time since the last new position and heading information was received. In block 2205, the component estimates the current position and heading of the airplane based on the actual position and heading information that was previously retrieved. One skilled in the art will appreciate that various different algorithms may be used to provide the estimates. For example, the algorithm may use a linear extrapolation of the last few positions based on the timer value. The algorithm may also factor in whether the airplane is turning based on the previous position and/or heading information and the ground speed of the airplane. The component then returns the estimated position and heading information.

FIG. 23 is a flow diagram that illustrates the processing of the evaluate horizontal limit component of the ATNS. This component determines whether the airplane is near the edge of a taxiway. This component is passed the estimated position of the airplane. In block 2301, the component retrieves information describing the location of the current taxiway. In block 2302, the component calculates the distance between the estimated position and the nearest edge of the taxiway. In decision block 2304, if the distance is greater than a specified limit, then the component returns an indication that the airplane is within an acceptable area of the taxiway, else the component returns an indication that the airplane is not within an acceptable area of the taxiway.

In one embodiment, the ATNS ensures smooth movement of the displayed map using a rotational smoothing algorithm and a movement smoothing algorithm. A sample pseudo code for a rotational smoothing algorithm (when the dynamic mode is heading up) is shown in Table 1 where

TABLE 1 select MRR from a predefined table based on zoom level, speed, and display update rate if (CAH ≠ CMH) HC = CAH − CMH if (HC < MRR) or (DL > MDL) CMH = CAH redraw map DL = 0 else add MRR to CMH redraw map DL = DL + 1 DL = display lag MDL = maximum display lag MRR = maximum rotation rate CAH = current aircraft heading CMH = current map heading HC = heading change

The rotational smoothing algorithm uses a maximum rotation rate for the map based on the zoom level, airplane speed, and update rate of the display. For example, if the zoom level is low, then a small maximum rotation rate may be used so the displayed map does not appear to jump around as the airplane turns. Similarly, if the update rate of the display is fast, then a small maximum rotation rate may be used because a large rotation amount can be effected by multiple updates over a short period. Also, if an airplane has a high speed, then a small maximum rotation rate may be used because the airplane can rotate very fast. One skilled in the art will appreciate that the maximum rotation rate for these and other factors can be empirically derived to provide a visually pleasing rotation.

The algorithm redraws the map whenever the heading of the airplane and the map are different. The algorithms redraws the map rotated by the change in heading but not exceeding the maximum rotation rate. If the rotation of the map is limited by the maximum rotation rate over several redraws because of a quick turn of the airplane, then the airplane and map headings may be very different. In such a case, the algorithm uses a “display lag” variable to count the number of successive redraws at the maximum rotation rate. If the number of display lags exceeds a maximum number, then the algorithm redraws the map to have the same heading as the airplane, even though it may exceed the maximum rotation rate, to effect an accurate, but nonsmooth rotation.

Sample pseudo code for the movement smoothing algorithm when the display refresh rate exceeds the input rate of the position and heading is shown in Table 2 where

TABLE 2 set FH and FS based on previous and current indications set JC to 0 if source corrects for jitter, otherwise 4 FH = ((FH * JC) + PHI) / (I + JC) FS = ((FS * JC) + PSI) / (I + JC) FHV is vector of FH and FS if (DRR > PRR) IF = DRR/PRR DP = CP + (FHV/IF) PHI = present heading indication FH = filtered heading JC = jitter correction PSI = present speed indication FS = filtered speed FHV = filtered heading vector DRR = display refresh rate PRR = refresh rate IF = interpolation factor DP = displayed position CP = current position

The movement smoothing algorithm smoothes the heading and speed of the aircraft. The algorithm initially removes jitter from the heading and speed readings by using the average of the last several (e.g., five) readings, if the display refresh rate is faster than the display rate of the readings, then the algorithm calculates an extrapolated position based on the last known position adjusted by an incremental position derived from the heading and speed divided by the ratio of the rates. For example, if the aircraft's heading is constant, its speed is 10 meters per second, the display refresh rate is four per second, and the position refresh rate is two per second, then the algorithm will add five meters (i.e., 10/(4/2)) to the last known position to generate the extrapolated position.

It will be appreciated that although specific embodiments of the ATNS have been described for purposes of illustration, various modifications may be made without deviating from the spirit and scope of the invention. For example, the ATNS may provide a user interface that uses various user interface elements, such as drop-down lists, scroll bars, text boxes, radio buttons, and so on, and uses various input devices, such as a trackball, a mouse, a keyboard, a light pen, a voice recognition system, and so on. One skilled in the art will appreciate that the ATNS may be useful for any type of air vehicle or aircraft as it taxis or otherwise moves about the taxiways or other ways of an airport. In addition, it may be useful to have the ATNS available to ground vehicles (e.g., maintenance and emergency vehicles) that travel around the taxiway or other ways of an airport. The ATNS has been described primarily in terms of taxiing after landing. The ATNS is also useful when taxiing before takeoff. A complete route of an airplane may include gate, taxi route, and runway whether taxiing before takeoff or taxiing after landing. Accordingly, the invention is not limited except by the appended claims. 

We claim:
 1. A method in an onboard computer for providing information for use in taxiing an aircraft at an airport, the method comprising: displaying, on a display, a map of the airport and a current position of the aircraft based on a current position information, the map showing taxiways of the airport; receiving, in an airport taxiway navigation system, position and direction information; estimating, using the airport taxiway navigation system, the current position information for the aircraft as the aircraft taxis at the airport; receiving, in the onboard computer, a taxi route specifying taxiways that the aircraft is to use to taxi at the airport, as specified by a taxi clearance received from at least one of: a ground control computer system, and a crewmember data entry device, wherein the taxi route comprises a sequential selection of each taxiway in the taxi route; highlighting on the map, using the onboard computer, a taxiway of the taxi route; determining, using the airport taxiway navigation system, if the aircraft is on the cleared taxi route; determining, using the airport taxiway navigation system, a track for the aircraft as it taxis; and generating a signal in the aircraft when the onboard computer determines that the aircraft has deviated from the taxi route.
 2. The method of claim 1 further comprising: receiving, in the onboard computer, positional information for the aircraft as the aircraft taxis at the airport; and displaying on the map an indication of a position of the aircraft as the aircraft taxis at the airport.
 3. The method of claim 2 wherein the map is displayed in a static mode.
 4. The method of claim 3 wherein the static mode is a north up mode.
 5. The method of claim 2 further comprising: receiving, in the onboard computer, directional information for the aircraft as it taxis at the airport; and displaying on the map an indication of a direction of the aircraft as it taxis at the airport.
 6. The method of claim 5 wherein the map is displayed in a dynamic mode.
 7. The method of claim 6 wherein the dynamic mode is a heading up mode.
 8. The method of claim 5 wherein the indication of the direction of the aircraft and the position of the aircraft is an image of an airplane.
 9. The method of claim 1 wherein the signal is a visual signal.
 10. The method of claim 1 wherein the signal is an audio signal.
 11. The method of claim 1 further comprising the onboard computer: receiving positional information for the aircraft; and generating a signal in the aircraft when the aircraft approaches a holdshort line.
 12. The method of claim 11 wherein the signal is a visual signal.
 13. The method of claim 11 wherein the signal is an audio signal.
 14. The method of claim 1 further comprising: as the taxiway is received, highlighting the taxiway on the map.
 15. The method of claim 1 including as the taxiway is received, displaying a name for the taxiway on the display.
 16. The method of claim 15 wherein a list of taxiway names on the display comprise the taxi route, and further wherein the list comprises the name for each taxiway selected, with the name for the taxiway presented in order of the sequential selection.
 17. The method of claim 1 wherein the displaying taxiways of the airport comprises presenting on the map, indications of only those taxiways that are logically possible next taxiways in the taxi route.
 18. The method of claim 1 wherein the displaying taxiways of the airport comprises displaying a name of each taxiway, wherein the name is displayed near a button on the display.
 19. The method of claim 1 wherein the displaying taxiways of the airport comprises highlighting a representation of each taxiway on the map on the display.
 20. The method of claim 1 including displaying a sequence of names of the taxiways in the taxi route.
 21. The method of claim 20 wherein the sequence is displayed in an area separate from the map on the display.
 22. The method of claim 20 further comprising receiving, in the onboard computer, position information for the aircraft as it taxis at the airport; and identifying, using the onboard computer, from the position information, the taxiway that the aircraft is currently on; and highlighting, using the onboard computer, the name of the taxiway.
 23. The method of claim 1 wherein the receiving of the taxi route further comprises: receiving, from a crewmember data entry device a selection of a button corresponding to each taxiway in the taxi route.
 24. The method of claim 1 wherein the map is displayed on a touch panel display and the receiving of the taxi route comprises receiving from a crewmember data entry device a selection of a displayed representation of each taxiway in the taxi route by touching the displayed representation.
 25. The method of claim 1 wherein the taxi route is received in the onboard computer without use of a crewmember data entry device.
 26. The method of claim 1 wherein the taxi route received by the onboard computer includes only major taxiways.
 27. The method of claim 1 further comprising: providing, in the onboard computer, a specification comprising a preferred taxi route for the airport and wherein the receiving of the taxi route includes the onboard computer receiving a selection of the preferred taxi route.
 28. The method of claim 27 wherein the preferred taxi route may be created and stored in the onboard computer by the onboard computer receiving inputs from a crewmember data entry device, specifying taxiways of the preferred taxi route.
 29. The method of claim 27 presenting, on the display, a sequence of names for the taxiways in the preferred taxi route when the onboard computer receives the selection of the preferred taxi route.
 30. The method of claim 27 wherein the selection of the preferred taxi route comprises first presenting on the display, a name assigned to each preferred taxi route.
 31. The method of claim 27 wherein the selection of the preferred taxi route comprises the onboard computer receiving inputs from a crewmember data entry device resulting in highlighting on the map the taxiway of the preferred taxi route or inputs to highlight a taxiway of another preferred route.
 32. The method of claim 1 wherein the receiving of the taxi route includes receiving voice input corresponding to a name for each taxiway in the route.
 33. The method of claim 1 further comprising: receiving, in the onboard computer, positional information for the aircraft as it taxis at the airport; receiving, in the onboard computer, an indication of a destination gate for the aircraft; and displaying the map of the airport so a current position of the aircraft and the destination gate are visible.
 34. The method of claim 1 including when displaying the map in a heading up mode, ensuring that labeling of items on the map is horizontally aligned.
 35. The method of claim 1 wherein the displaying of the map comprises the onboard computer: receiving position information for the aircraft, identifying the airport based on the position information, and selecting the map for the airport.
 36. The method of claim 1 further comprising the onboard computer: receiving an indication to display a satellite view of the airport; retrieving the satellite view; and displaying, on the display, the satellite view of the airport.
 37. A method for alerting when an aircraft at an airport deviates from at least one of: a horizontal limit on a current taxiway, and a cleared taxi route, the method comprising: displaying, on a display, a map of the airport, the map showing taxiways of the airport; receiving, in an airport taxiway navigation system, the cleared taxi route comprising taxiways that the aircraft is to use to taxi at the airport, as specified by a taxi clearance; highlighting on the map, using the airport taxiway navigation system, a taxiway of the cleared taxi route; receiving, in the airport taxiway navigation system, position information for the aircraft as it taxis at the airport; identifying the current taxiway as being the taxiway that the aircraft is currently on; determining, using the airport taxiway navigation system, if the aircraft is on the cleared taxi route; determining, using the airport taxiway navigation system, a track for the aircraft as it taxis; determining the horizontal limit on the current taxiway, based at least on: the current taxiway, and the track, the horizontal limit on the current taxiway indicating when the aircraft is near an edge of the current taxiway; and alerting, when the aircraft deviates from at least one of: the horizontal limit on the current taxiway, and the cleared taxi route.
 38. The method of claim 1 wherein the map is displayed in an align-to-runway mode.
 39. The method of claim 38 wherein the onboard computer receives a runway to align to from a crewmember data entry device.
 40. The method of claim 38 wherein the align-to-runway is a landing runway.
 41. The method of claim 38 wherein the map automatically switches to a heading up mode when the aircraft lands.
 42. The method of claim 38 wherein the map is automatically switches to the align-to-runway mode when the aircraft takes off.
 43. The method of claim 1 further comprising: receiving, in the onboard computer, from a crewmember input device, an annotation for the map; and displaying the annotation on the map.
 44. The method of claim 43 wherein the annotation is received via a freehand drawing device.
 45. The method of claim 43 wherein the annotation is received via placement of an icon.
 46. The method of claim 43 wherein the annotation is received via a text box.
 47. The method of claim 43 wherein the annotation is associated with a position on the map.
 48. The method of claim 43 wherein the annotation is scaled when the map is scaled.
 49. The method of claim 43 wherein the annotation is panned as the map is panned. 